Skip to content

Update node version to 24.x in CI#328

Merged
arr00 merged 1 commit intomasterfrom
chore/update-npm-version-ci
Mar 16, 2026
Merged

Update node version to 24.x in CI#328
arr00 merged 1 commit intomasterfrom
chore/update-npm-version-ci

Conversation

@arr00
Copy link
Copy Markdown
Member

@arr00 arr00 commented Mar 16, 2026

Summary by CodeRabbit

  • Chores
    • Updated Node.js version from 20.x to 24.x in the build environment.

@arr00 arr00 requested a review from a team as a code owner March 16, 2026 18:18
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 16, 2026

Deploy Preview for confidential-tokens ready!

Name Link
🔨 Latest commit e6c79b5
🔍 Latest deploy log https://app.netlify.com/projects/confidential-tokens/deploys/69b8496cf293860008d8ddb1
😎 Deploy Preview https://deploy-preview-328--confidential-tokens.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 16, 2026

Walkthrough

The Node.js version in the GitHub Actions setup action was updated from 20.x to 24.x, affecting the build environment configuration used across CI/CD workflows.

Changes

Cohort / File(s) Summary
GitHub Actions Configuration
.github/actions/setup/action.yml
Updated Node.js version from 20.x to 24.x in the setup-node step.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • james-toussaint

Poem

🐰 A hop and a skip through versions new,
From twenty to twenty-four, a Node.js breakthrough!
The rabbits rejoice, their tools now so bright,
With faster updates and newer delights! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately summarizes the main change: updating the Node.js version from 20.x to 24.x in the CI configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/update-npm-version-ci
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

You can disable poems in the walkthrough.

Disable the reviews.poem setting to disable the poems in the walkthrough.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/actions/setup/action.yml (1)

9-14: ⚠️ Potential issue | 🟠 Major

Include Node major version in cache key to prevent cross-runtime node_modules reuse.

Upgrading to node-version: 24.x while keeping the cache key unchanged creates a risk of restoring node_modules built under a different Node major version. Native modules have version-specific ABIs that break across Node majors, causing flaky CI failures on subsequent runs that restore stale cache entries.

Proposed fix
-        key: npm-v3-${{ hashFiles('**/package-lock.json') }}
+        key: npm-v3-node24-${{ runner.os }}-${{ hashFiles('**/package-lock.json') }}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/actions/setup/action.yml around lines 9 - 14, The cache key for the
actions/cache step ('uses: actions/cache@v4') currently only hashes
package-lock.json and must include the Node major version to avoid restoring
node_modules built for a different runtime; update the cache 'key' expression
(the key field on the cache step) to incorporate the Node major (e.g., include
the node-version or its major) so the cache is namespaced per Node runtime
alongside the existing hash, ensuring separate caches for different Node majors.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In @.github/actions/setup/action.yml:
- Around line 9-14: The cache key for the actions/cache step ('uses:
actions/cache@v4') currently only hashes package-lock.json and must include the
Node major version to avoid restoring node_modules built for a different
runtime; update the cache 'key' expression (the key field on the cache step) to
incorporate the Node major (e.g., include the node-version or its major) so the
cache is namespaced per Node runtime alongside the existing hash, ensuring
separate caches for different Node majors.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5a63f5cd-6406-477c-9ab2-fcebbf26649a

📥 Commits

Reviewing files that changed from the base of the PR and between 5abcb1c and e6c79b5.

📒 Files selected for processing (1)
  • .github/actions/setup/action.yml

@arr00 arr00 merged commit 933f7b1 into master Mar 16, 2026
15 checks passed
@arr00 arr00 deleted the chore/update-npm-version-ci branch March 16, 2026 18:25
arr00 added a commit that referenced this pull request Mar 16, 2026
arr00 added a commit that referenced this pull request Apr 1, 2026
* Start release candidate

* Fix local docs generation (#320)

* remove properties symlink

* add properties.js

* lint fix

* Remove backwards compatibility from Batcher (#321)

* Remove backwards compatibility from Batcher

* Apply suggestion from @arr00

* Validate `fromToken` and `toToken` on construction (#322)

* Validate `fromToken` on construction

* use `ERC165Checker`

* check toToken as well

* directly validate to and from token

* Add additional functions to `IERC7984ERC20Wrapper` (#323)

* remove incorrect docs on `unwrap` function

* add finalize unwrap and rate to wrapper interface

* update batcher to use unwrap request ids instead of unwrap amounts

* add `unwrapAmount` to wrapper interface for unwrap request introspection

* additional docs

* call getter for `unwrapAmount` in `finalizeUnwrap`

* update events and errors appropriately

* remove `ERC7984ERC20Wrapper` import

* fix import order

* Move events to interface from `ERC7984ERC20Wrapper`

* add note on request id for `unwrap`

* change mapping to be of `bytes32` identifiers

* add changeset

* Allow claiming on behalf of another account in batcher (#324)

* Allow claiming on behalf of another account in batcher

* revert on claim if users not part of the batch

* add error on quit too

* Add additional warnings to the batcher (#325)

* Return a bytes32 unwrap id from the `_unwrap` function in `BatcherConfidential` (#326)

* Return a bytes32 unwrap id from the `_unwrap` function in `BatcherConfidential`

* modify warning

* Document possible rounding down of user deposits (#327)

* Document possible rounding down of user deposits

* add contract level comment as well

* up

* Release v0.4.0 (rc) (#318)

* Release v0.4.0 (rc)

* update changelog

* update changelog

* Apply suggestion from @james-toussaint

Co-authored-by: James Toussaint <33313130+james-toussaint@users.noreply.github.com>

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Arr00 <13561405+arr00@users.noreply.github.com>
Co-authored-by: James Toussaint <33313130+james-toussaint@users.noreply.github.com>

* Update node version to 24.x in CI (#328)

* Exit release candidate

* Release v0.4.0 (#335)

* Release v0.4.0

* update changelog

* remove changelog duplicate

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Arr00 <13561405+arr00@users.noreply.github.com>

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Arr00 <13561405+arr00@users.noreply.github.com>
Co-authored-by: James Toussaint <33313130+james-toussaint@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant